Skip to content

Fix density matrix trace drift after measurement collapse#8171

Open
anshjaiswal12 wants to merge 3 commits into
quantumlib:mainfrom
anshjaiswal12:fix/density-matrix-trace-5916
Open

Fix density matrix trace drift after measurement collapse#8171
anshjaiswal12 wants to merge 3 commits into
quantumlib:mainfrom
anshjaiswal12:fix/density-matrix-trace-5916

Conversation

@anshjaiswal12

@anshjaiswal12 anshjaiswal12 commented Jun 30, 2026

Copy link
Copy Markdown

Summary

After a measurement collapse, measure_density_matrix divides by the outcome probability. Floating-point error can leave the density matrix with trace slightly ≠ 1. Reusing final_density_matrix as initial_state compounds that drift (gh-5916).

Renormalize by trace after collapse and add regression tests.

Fixes #5916

Tests

  • test_density_matrix_trace_after_each_moment_gh5916
  • test_density_matrix_trace_stable_under_repeated_simulation
  • test_density_matrix_trace_stable_across_circuit_families
  • test_density_matrix_trace_repeated_simulation_performance_smoke

AI disclosure: Cursor IDE was used only to read/search the codebase and help debug the issue. All code in this PR was written and reviewed by me.

Post-measurement normalization by outcome probability can leave the
density matrix with trace slightly off 1; reusing it as initial_state
compounds the error. Renormalize by trace after collapse and add
regression tests that check trace at each simulation step.

Fixes quantumlib#5916
@anshjaiswal12 anshjaiswal12 requested a review from a team as a code owner June 30, 2026 07:09
@anshjaiswal12 anshjaiswal12 requested a review from dstrain115 June 30, 2026 07:09
@google-cla

google-cla Bot commented Jun 30, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@github-actions github-actions Bot added the size: M 50< lines changed <250 label Jun 30, 2026
Pull post-measurement trace correction into _renormalize_density_matrix_trace,
use np.isclose for the zero-trace guard, and deduplicate the quantumlibgh-5916 regression
circuit in tests.
@codecov

codecov Bot commented Jul 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.60%. Comparing base (d7f55d3) to head (c15b07a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8171      +/-   ##
==========================================
- Coverage   99.60%   99.60%   -0.01%     
==========================================
  Files        1118     1118              
  Lines      101356   101409      +53     
==========================================
+ Hits       100956   101004      +48     
- Misses        400      405       +5     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Collapse _assert_density_matrix_trace_one signature to one line to
satisfy the incremental format check on CI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: M 50< lines changed <250

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Density matrix traces not remaining at 1 after certain operations

1 participant